NetNews Offline 2/NetNews Offline Volume 2.iso/news/comp/sys/amiga/networking/503

Internet Message Format | 1996-08-05 | 25.3 KB

Path: hearst.acc.Virginia.EDU!adastra!mbs
Newsgroups: comp.sys.amiga.networking
From: [e-mail] (Michael B. Smith)
Subject: Re: Best Mail Program for use with SLIP, SMTP, POP, AmiTCP?
Distribution: world
References: <4bu7f9$[e-mail]> <[e-mail]> <[e-mail]> <4ddmbn$[e-mail]>
X-NewsReader: GRn 3.0 January 12, 1996
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <[e-mail]>
Date: Mon, 15 Jan 96 18:16:50 EDT
Organization: Only if you insist...

In article <4ddmbn$[e-mail]> [e-mail] (Frederick V. Heitkamp) writes:
> : at once than by using environment variables? With a single, integrated program
> : (like THOR) it makes sense to encapsulate all the settings in one file, and
> : use a prefs editor, but if you have a big bunch of separate applications for
> : different tasks (UUCP, NNTP, POP, SMTP etc.), the cleanest way is to define
> : global environment variables which are simple and accessible to all programs.
> : People are scared off by setting them all up, though.
>
> Folks writing internet apps for the Amiga should use UUCP as their standard for
> specifying setups then.  How about a complete UUCP FAQ and guide directed
> toward the AmiTCP/internet crowd with plenty of  background and tutorial
> information?

Having written much of the first generation of Internet software, I did just
that. The GRn guide was pretty complete, as is the INetUtils documentation.
Granted, they weren't the easiest things in the world to read.

The document below, which I've posted several times recently, helps a great
deal. It applies to I-Net 225, INetUtils 1.4 (the last freeware version) and
GRn 2.1 (the last freeware version).
--
  //   Michael B. Smith
\X/    [e-mail]

@database ConfigVars.guide
@Author "Michael B. Smith"
@$VER: ConfigVars.guide 1.0 (29.12.95)
@Width 80
@SmartWrap
#@Font topaz.font 11

@Node Main "ConfigVars"
@{b}ConfigVars@{ub}                                @{b}ConfigVars@{ub}


@{b}INet:s/Config@{ub} is intended as a general purpose registry for program
configuration, where those programs are TCP-stack related. As such, we document
all of the variables which I-Net 225 uses.


The user does not have to use the @{b}INet:s/Config@{ub} file for setting
configuration information. All values will first be read from the program's
environment, before any value in that file is checked. In order of hierarchy,
the following applies:


    a program's local environment

    the global environment

    the contents of @{b}INet:s/Config@{ub}


If you are using any of the @{b}INetUtils@{ub}, @{b}GRn@{ub}, or @{b}GMail@{ub} programs,
this information also applies to you. If your version was compiled
for AmiTCP or UUCP, instead of for I-Net 225, the filename used is S:UUConfig.


If your TCP/IP stack has been installed correctly, then you are not @{u}required@{uu} to
set any values in this file. The only required settings are:


    @{"User" link user}


    @{"Hostname" link hostname}


and these are set by both available TCP/IP stacks in the global environment.


However, if you using an @{u}old@{uu} version of INetUtils (the freeware
version 1.4 or before) you should read @{"this section" link oldrequirements} of
this manual.


Configuration falls into three categories: general, mail, and news. Select the
button for the area in which you are interested.


    @{"General" link configgeneral}


    @{"Mail" link configmail}


    @{"News" link confignews}


There are also some configuration variables commonly used by other programs.
Click @{"here" link otherstuff} for descriptions of those.


@EndNode

@Node oldrequirements "Requirements for INetUtils 1.4 and prior"


This is @{u}only@{uu} for @{b}old@{ub} versions of INetUtils and GRn.


Freeware versions of INetUtils required more configuration, due to having
fewer defaults defined. In general, you @{u}had@{uu} to configure these
items:


    @{u}General@{uu}


    User

    Nodename

    Hostname

    LibDir


    @{u}Mail@{uu}


    SMTPMailDir

    SMTPSmarterHost

    SMTPSpoolDir


    @{u}News@{uu}


    NewsDir


GRn versions prior to 3.0 also required UUSpool, @{u}only@{uu} to define
where to place its logfile.


However, this is not as bad as it may appear. Nodename should be, for all
intents and purposes, the same as Hostname. The other values need only to
be set once, and then can be left alone. User and Hostname should be set
by your TCP/IP stack.


Contrary to some beliefs, INetUtils does not require UUCP to be installed
before. For explanations of each of these values, see the descriptive text
in other places in this document.


Thus, a simple script like that shown below, running after your network
connection is active, and it will take care of any problems.


Note that there are two scripts,
the first is for AS225, the other is for AmiTCP. They differ only in
selected directory locations. If you have I-Net 225, or the commercial
version of INetUtils, you do not need to execute these scripts. Also note
that you can "assign inet: amitcp:" and run the AS225 version just as
easily as the AmiTCP version.


It is recommended that you select a proper value for SMTPSmarterhost; however,
the value below will get you running. Your network provider can tell you what
the correct value is.


AS225 script:


    setenv libdir inet:s

    setenv uuspool inet:

    setenv nodename $hostname

    if not exists inet:mail

        makedir inet:mail

    endif

    setenv smtpmaildir inet:mail

    if not exists inet:mailspool

        makedir inet:mailspool

    endif

    setenv smtpmailspool inet:mailspool

    if "$smtpsmarterhost" eq ""

        setenv smtpsmarterhost dummy

    endif

    if "$smtpsmarterhost" eq "*$smtpsmarterhost"

        setenv smtpsmarterhost dummy

    endif

    if not exists inet:news

        makedir inet:news

    endif

    setenv newsdir inet:news


AmiTCP script:


    setenv libdir amitcp:db

    setenv uuspool amitcp:

    setenv nodename $hostname

    if not exists amitcp:mail

        makedir amitcp:mail

    endif

    setenv smtpmaildir amitcp:mail

    if not exists amitcp:mailspool

        makedir amitcp:mailspool

    endif

    setenv smtpmailspool amitcp:mailspool

    if "$smtpsmarterhost" eq ""

        setenv smtpsmarterhost dummy

    endif

    if "$smtpsmarterhost" eq "*$smtpsmarterhost"

        setenv smtpsmarterhost dummy

    endif

    if not exists amitcp:news

        makedir amitcp:news

    endif

    setenv newsdir amitcp:news


@Endnode

@Node configgeneral "General Configuration"


General configuration elements affect both news and mail, or even
other aspects of the TCP stack.


The relevant items are:


    @{"User" link user}


    @{"Realname" link realname}


    @{"Nodename" link nodename}


    @{"Domainname" link domainname}


    @{"Hostname" link hostname}


    @{"Logfile" link logfile}


    @{"LibDir" link libdir}


    @{"TimeZone" link timezone}


@EndNode

@Node configmail "Mail Configuration"


Mail configuration variables affect only mail. If you are not using
features dealing with mail, they need not be set.


The relevant items are:


    @{"SMTPPost" link smtppost}


    @{"SMTPSpoolDir" link smtpspooldir}


    @{"SMTPMailDir" link smtpmaildir}


    @{"SMTPRMail" link smtprmail}


    @{"SMTPDelay" link smtpdelay}


    @{"SMTPRoute" link smtproute}


    @{"SMTPAlwaysQueue" link smtpalwaysqueue}


    @{"HostAliases" link hostaliases}


    @{"CheckUser" link checkuser}


    @{"SmartFrom" link smartfrom}


    @{"UUCPSendMail" link uucpsendmail}


    @{"MailReadyCMD" link mailreadycmd}


@EndNode

@Node confignews "News Configuration"


News configuration variables affect only news. If you are not using features
dealing with news, they need not be set.


The relevant items are:


    @{"NewsDir" link newsdir}


    @{"NNTPRNews" link nntprnews}


    @{"NNTPServer" link nntpserver}


    @{"NNTPUserid" link nntpuserid}


    @{"NNTPPassword" link nntppassword}


@EndNode

@Node user "Configuration - User"


Local Environment:    set user mbs

Global Environment:    setenv user mbs

Configuration File:    user mbs

Default:        none


"Username" is a deprecated synonym for "user".


@{b}User@{ub} defines the login identity of the person using the computer. It is
normally set by the login program of the TCP/IP stack. @{b}User@{ub} must
exist in the password file.


@{b}User@{ub} is used by various mail and news programs to construct the From: and/or
Sender: headers used for identification purposes.


I-Net 225 requires that the uid and gid specified in @{b}INet:s/inet.config@{ub} for
@{b}User@{ub} also match the entries in the password file.


@EndNode

@Node realname "Configuration - Realname"


Local Environment:    set realname Mondo B. Sasquatch

Global Environment:    setenv realname Mondo B. Sasquatch

Configuration File:    Realname Mondo B. Sasquatch

Default:        none


The @{b}Realname@{ub} is the proper name by which a computer user is to be known.
It is used by various mail and news programs to construct the From: and/or
Sender: headers used for identification purposes.


@EndNode

@Node nodename "Configuration - Nodename"


Local Environment:    set nodename mycomputer

Global Environment:    setenv nodename mycomputer

Configuration File:    Nodename mycomputer

Default:        none


Use of this is not recommended. Use @{"Hostname" link hostname} instead.


The @{b}Nodename@{ub} is normally the first piece of the @{b}Hostname@{ub} of a computer.
For example, with a @{b}Hostname@{ub} of "mycomputer.somedomain.com" the @{b}Nodename@{ub}
would be "mycomputer". The @{b}Domainname@{ub} would be ".somedomain.com".


@EndNode

@Node domainname "Configuration - Domainname"


Local Environment:    set domainname .somedomain.com

Global Environment:    setenv domainname .somedomain.com

Configuration File:    Domainname .somedomain.com

Default:        none


Use of this is not recommended. Use @{"Hostname" link hostname} instead.


The @{b}Domainname@{ub} is normally the rest of the @{b}Hostname@{ub} of a computer after
the @{b}Nodename@{ub}. For
example, with a @{b}Hostname@{ub} of "mycomputer.somedomain.com" the @{b}Nodename@{ub} would
be "mycomputer". The @{b}Domainname@{ub} would be ".somedomain.com".


@EndNode

@Node hostname "Configuration - Hostname"


Local Environment:    set hostname mycomputer.com

Global Environment:    setenv hostname mycomputer.com

Configuration File:    Hostname mycomputer.com

Default:        none


Be very careful if you set this. Normally, this should be set by the
TCP/IP stack, and you should not modify it.


@{b}Hostname@{ub} is the fully qualified domain name of the current computer.


Various programs must be able to obtain the @{b}Hostname@{ub} of the computer.
They will try to do this first from the @{b}Hostname@{ub} string, next
from a combination of @{b}NodeName@{ub} and @{b}DomainName@{ub}, and finally
from the TCP/IP stack API call @{b}gethostname()@{ub}. If all of these
fail, the programs will display an error message and terminate.


@EndNode

@Node logfile "Configuration - Logfile"


Local Environment:    set logfile Work:INet225-logfile

Global Environment:    setenv logfile Work:INet225-logfile

Configuration File:    logfile Work:INet225-logfile

Default I-Net 225:    INet:Logfile

Default AmiTCP:     AmiTCP:Logfile

Default UUCP:        UUSpool:Logfile


Various pieces of information concerning status and errors are
stored in the @{b}Logfile@{ub}. You should examine/flush/empty this file
on a regular basis.


If you do not want logging information stored, you may set the
@{b}Logfile@{ub} to NIL:.


@EndNode


@Node libdir "Configuration - LibDir"


Local Environment:    set libdir INet:s

Global Environment:    setenv libdir INet:s

Configuration File:    LibDir INet:s

Default I-Net 225:    INet:s

Default AmiTCP:     UULib:

Default UUCP:        UULib:


The @{b}LibDir@{ub} is the directory where certain files are stored. The files are:


    <user>.header

    <user>.signature

    news/active


The various mail and news programs will search for these files in that
directory.


@EndNode

@Node organization "Configuration - Organization"


Local Environment:    set organization Not here, not ever.

Global Environment:    setenv organization Not here, not ever.

Configuration File:    Organization Not here, not ever.

Default:        none


@{b}Organization@{ub} is an optional header for mail and news messages. If
defined, the various mail and news programs will include this string
as that header.


It typically denotes a company affiliation.


@EndNode

@Node newsdir "Configuration - NewsDir"


Local Environment:    set newsdir INet:News

Global Environment:    setenv newsdir INet:News

Configuration File:    NewsDir INet:News

Default I-Net 225:    INet:News

Default AmiTCP:     AmiTCP:News

Default UUCP:        UUNews:


@{b}NewsDir@{ub} is where transferred news articles are stored.


@EndNode

@Node nntprnews "Configuration - NNTPRnews"


Local Environment:    set nntprnews uucp:c/news -p

Global Environment:    setenv nntprnews uucp:c/rnews -p

Configuration File:    NNTPRNews uucp:c/rnews -p

Default:        none


@{b}NNTPxfer@{ub} supports a configuration variable named @{b}NNTPRNEWS@{ub}. When
defined, @{b}NNTPxfer@{ub} will call that program, with each incoming news
article on standard input, and allow it to file that article. This
allows the input to be filed along with UUCP news, and vice versa.


For example, to be used with the AmigaUUCP RNEWS, the definition
would be:


    SetEnv NNTPRNews uucp:c/rnews -p


with the -p indicating that this is a "postnews" call. Note that for
maximum speed and efficiency, RNEWS should be a resident program.


If the BATCH parameter is set for @{b}NNTPXfer@{ub}, then the correct setting would be:


    SetEnv NNTPRNews uucp:c/rnews


since more than one article will be contained in the input to RNEWS.
Using the BATCH mode is much more efficient for a large feed than
otherwise.


@EndNode

@Node nntpserver "Configuration - NNTPServer"


Local Environment:    set nntpserver news.somedomain.com

Global Environment:    setenv nntpserver news.somedomain.com

Configuration File:    NNTPServer news.somedomain.com

Default:        none


To transfer articles via NNTP (Network News Transfer Protocol) requires
that they be obtained from another computer. That other computer is the
@{b}NNTPServer@{ub}.


Your network provider will have to tell you the correct value to set
for the @{b}NNTPServer@{ub}.


@EndNode

@Node nntpuserid "Configuration - NNTPUserid"


Local Environment:    set nntpuserid mbs

Global Environment:    setenv nntpuserid mbs

Configuration File:    NNTPUserid mbs

Default:        none


Most network providers will not allow anonymous or unauthorized access
to their NNTP server. Using the @{b}NNTPUserid@{ub} and @{b}NNTPPassword@{ub} configuration
variables allows you to identify yourself to the NNTP server, based on the
"AUTHINFO USER" protocol.


Your network provider will assign you a @{b}NNTPUserid@{ub} and an @{b}NNTPPassword@{ub}.


@EndNode

@Node nntppassword "Configuration - NNTPPassword"


Local Environment:    set nntppassword somepassword

Global Environment:    setenv nntppassword somepassword

Configuration File:    NNTPPassword somepassword

Default:        none


Most network providers will not allow anonymous or unauthorized access
to their NNTP server. Using the @{b}NNTPUserid@{ub} and @{b}NNTPPassword@{ub} configuration
variables allows you to identify yourself to the NNTP server, based on the
"AUTHINFO USER" protocol.


Your network provider will assign you a @{b}NNTPUserid@{ub} and an @{b}NNTPPassword@{ub}.


@EndNode

@Node smtppost "Configuration - SMTPPost"


Local Environment:    set smtppost INet:c/smtppost

Global Environment:    setenv smtppost INet:c/smtppost

Configuration File:    SMTPPost INet:c/SMTPPost

Default:        SMTPpost


Setting this allows you to identify where the @{b}SMTPPost@{ub} binary
resides, if it is not in your default path.


@EndNode

@Node smtpspooldir "Configuration - SMTPSpoolDir"


Local Environment:    set smtpspooldir INet:MailSpool

Global Environment:    setenv smtpspooldir INet:MailSpool

Configuration File:    SMTPSpoolDir INet:MailSpool

Default I-Net 225:    INet:MailSpool

Default AmiTCP:     AmiTCP:MailSpool


@{b}SMTPSpoolDir@{ub} is the directory where SMTP spool files are to be
located. If @{b}SMTPpost@{ub} cannot locate a destination host, it places
the articles in this directory, and retries sending the messages on
a regular basis. It @{u}may not@{uu} be shared with the UUCP spool directory, as the
batch files are of a different format.


This directory must exist.


@EndNode

@Node smtpmaildir "Configuration - SMTPMailDir"


Local Environment:    set smtpmaildir INet:Mail

Global Environment:    setenv smtpmaildir INet:Mail

Configuration File:    SMTPMailDir INet:Mail

Default I-Net 225:    INet:Mail

Default AmiTCP:     AmiTCP:Mail

Default UUCP:        UUMail:


The directory where local mail is to be stored. This directory must
exist.


This directory may be shared with UUCP mailboxes and folders.


@EndNode

@Node smtpsmarterhost "Configuration - SMTPSmarterHost"


Local Environment:    set smtpsmarterhost dummy

Global Environment:    setenv smtpsmarterhost dummy

Configuration File:    SMTPSmarterHost dummy

Default:        none


@{b}SMTPSmarterHost@{ub} is a SMTP host where mail is sent if a destination
host named in an address is not reachable. It is presumed to be an
Internet host which has better routing information than does the host
running this @{b}SMTPd@{ub}. If not specified, no smarterhost routing will
be done.


@EndNode

@Node smtprmail "Configuration - SMTPRMail"


Local Environment:    set smtprmail uucp:c/sendmail -r

Global Environment:    setenv smtprmail uucp:c/sendmail -r

Configuration File:    SMTPRMail uucp:c/sendmail -r

Default:        SMTPPost -r


@{b}SMTPRMail@{ub} defines the program that will deliver mail which was
destined for this host. Typically, it is a copy of @{b}SMTPpost@{ub}, renamed
to RSMTP or SMTPpost with the -r argument.


@EndNode

@Node smtpdelay "Configuration - SMTPDelay"


Local Environment:    set smtpdelay 30

Global Environment:    setenv smtpdelay 30

Configuration File:    SMTPDelay 30

Default:        120


@{b}SMTPd@{ub} uses the @{b}SMTPDelay@{ub} environment variable to determine how long
to wait between scans of @{b}SMTPSpoolDir@{ub}. The
default value causes @{b}SMTPd@{ub} to wait two minutes between each scan of the
spool directory. Note that @{b}SMTPd@{ub} will not try to ship a specific
file more often than two times @{b}SMTPDelay@{ub}. That is, for the default,
a file will not be attempted more often than once every four minutes.


@EndNode

@Node smtproute "Configuration - SMTPRoute"


Local Environment:    set smtproute mx,smtp

Global Environment:    setenv smtproute mx,smtp

Configuration File:    SMTPRoute mx,smtp

Default:        mx,smtp,smarterhost,uucp


@{b}SMTPRoute@{ub} may have any of four values, comma or space separated.
The values are:


    MX

    SMTP

    SmarterHost

    UUCP


These values control the way @{b}SMTPpost@{ub} attempts to deliver mail to
remote hosts.


MX indicates to use the MX record (from DNS) to deliver the mail
to the destination host via the forwarding host specified in the
MX record.


SMTP indicates to attempt to deliver the mail directly to the
remote host.


SmarterHost indicates to deliver the mail to the host specified
as the @{b}SMTPSmarterHost@{ub} configuration variable. If @{b}SMTPSmarterHost@{ub} is
not specified, then this type of transfer will not occur, and
a warning will be issued if Smarterhost is specified.


UUCP indicates to deliver the mail using the mail program specified
as the @{b}UUCPSendMail@{ub} configuration variable. If @{b}UUCPSendMail@{ub} is not
specified, then this type of transfer will not occur, and a warning
will be issued if UUCP is specified.


Note: the freeware version of @{b}SMTPpost@{ub} in INetUtils 1.4 only utilized the first
MX record for any destination host.


@EndNode

@Node smtpalwaysqueue "Configuration - SMTPAlwaysQueue"


Local Environment:    set smtpalwaysqueue y

Global Environment:    setenv smtpalwaysqueue y

Configuration File:    SMTPAlwaysQueue yes

Default:        no


When set to "yes", then @{b}SMTPpost@{ub} will act as if -Q was passed.
The default is "no".


When set, @{b}SMTPpost@{ub} will not attempt to deliver mail directly,
but will allow @{b}SMTPd@{ub} to process the mail as part of it's regular
cycle.


This has the advantage of crash protection -- if a mail message does
not go through @{b}SMTPd@{ub}, then it may reside only in memory. If the computer
crashes for any reason while @{b}SMTPPost@{ub} is processing a message, then it
is "lost". If it is queued on disk, then it will still exist, and will
be reprocessed later.


@EndNode

@Node hostaliases "Configuration - HostAliases"


Local Environment:    set hostaliases othercomputer.com

Global Environment:    setenv hostaliases othercomputer.com

Configuration File:    HostAliases othercomputer.com

Default:        none


The @{b}HostAliases@{ub} variable contains other hostnames which are the
local host. For example, if your host is "x.y.z", but you also
need to accept mail to "zz.zz" as local to you, you should set
that in @{b}HostAliases@{ub}.


In general, put "localhost,[ip.address],ip.address" plus any
others into @{b}HostAliases@{ub}.


The comparison is *not* case sensitive.


Note: The freeware version of @{b}SMTPpost@{ub} in INetUtils 1.4 only allowed two
entries in @{b}Hostaliases@{ub}.


@EndNode

@Node smartfrom "Configuration - SmartFrom"


Local Environment:    set smartfrom y

Global Environment:    setenv smartfrom y

Configuration File:    SmartFrom yes

Default:        no


The very first line of a mail message is the envelope. This
option controls the format of the envelope. Normally, it
looks like this (with "SmartFrom no"):


    From mbs Sat Jul 1 1995 17:42:12 (EST) remote from mycomputer.com


and with "SmartFrom yes", it looks like this:


    From [e-mail] Sat Jul 1 1995 17:42:12 (EST)


which is relevant to some mail readers (but very few).


Note that this is @{u}not@{uu} the same thing as the "From:" header.


"SmartUUCP" is a deprecated synonym for @{b}SmartFrom@{ub}.


@EndNode

@Node checkuser "Configuration - CheckUser"


Local Environment:    set checkuser INet:c/checkuser

Global Environment:    setenv checkuser INet:c/checkuser

Configuration File:    CheckUser INet:c/CheckUser

Default:        none


The @{b}CheckUser@{ub} variable defines a program which is executed for
each piece of incoming mail to validate whether the destination user actually
exists. To wit:


        CheckUser userid


@{b}SMTPpost@{ub} checks the first character of standard output from the
program (stdout). If it is a '*', then the user is deemed invalid.
Any other output is defined as the fully-specified filename to
be used as the mailbox for the destination user.


Note: this feature is not available in the freeware version of
@{b}SMTPpost@{ub} in INetUtils 1.4.


@EndNode

@Node timezone "Configuration - TimeZone"


Local Environment:    set timezone (+0400)

Global Environment:    setenv timezone (+0400)

Configuration File:    TimeZone (+0400)

Default:        none


When required to generate a Date: header, @{b}SMTPpost@{ub} and @{b}NNTPpost@{ub} will generate
an ARPA date-time stamp as specified in RFC-822 (and modified by
RFC-1123). This is the format:


    Wed, 13 Oct 1993 18:52:04 EST


The @{b}TimeZone@{ub} variable would contain, for example, the "EST" as
shown above.


There are relatively few "legal" timezones specified in the
RFC. Some mail systems, and similarly some news systems, will
reject a Date which does not have a legal @{b}TimeZone@{ub}. To ensure
this "legality" a @{b}TimeZone@{ub} of the form:


    (+0500)


is preferred, @{u}with@{uu} the literal parentheses. The resulting
header would be:


    Wed, 13 Oct 1993 18:52:04 (+0500)


@EndNode

@Node uucpsendmail "Configuration - UUCPSendMail"


Local Environment:    set uucpsendmail uucp:c/rmail

Global Environment:    setenv uucpsendmail uucp:c/rmail

Configuration File:    UUCPSendMail uucp:c/rmail

Default:        none


If the @{b}SMTPRoute@{ub} variable includes UUCP as a part of it, then this
variable must be defined. It defines the program name of the UUCP
mail program (typically @{b}UUCP:C/RMail@{ub}).


@EndNode

@Node mailreadycmd "Configuration - MailReadyCMD"


Local Environment:    set mailreadycmd

Global Environment:    setenv mailreadycmd

Configuration File:    MailReadyCMD

Default:        none


@{b}SMTPpost@{ub} will attempt to run a command named by the
@{b}MailReadyCMD@{ub} configuration variable when delivering @{u}local@{uu} mail. The format
of the command is:


    MAILREADYCMD -x T:MailRdy


@{b}SMTPpost@{ub} will also cause the signal of a public message port named
"T:MailRdy" if it can be found.


@EndNode

@Node otherstuff "Configuration - Other Variables"


Other programs also use configuration information in the way described in this
document. Here are some common items used.
@{lindent 5}


ReplyTo
@{lindent 10}


Defines the address that an email reply to an email message or news article
should be sent to. For example:


    set ReplyTo [e-mail]
@{lindent 5}


WWW_Home
@{lindent 10}


The "Home Page" that should be accessed when a user clicks on the "Home" button
in a Web browser.
@{lindent 5}


HTTP_Proxy
@{lindent 10}


In order to get through a firewall, many users have to redirect World Wide Web
requests. This one allows a HTTP request to be redirected.
@{lindent 5}


FTP_Proxy
@{lindent 10}


In order to get through a firewall, many users have to redirect World Wide Web
requests. This one allows a FTP request to be redirected.
@{lindent 5}


GOPHER_Proxy
@{lindent 10}


In order to get through a firewall, many users have to redirect World Wide Web
requests. This one allows a Gopher request to be redirected.
@{lindent 5}


PopHost
@{lindent 10}


Some POP-mail clients use PopHost to the define the computer to access
to get POP mail.
@{lindent 5}


PopUser
@{lindent 10}


Some POP-mail clients use PopUser as the authorization name sent
to the POP host.
@{lindent 5}


PopPassword
@{lindent 10}


Some POP-mail clients use PopPassword as the password for "PopUser".


@EndNode